<?php
/**
 * <https://y.st./>
 * Copyright © 2019 Alex Yst <mailto:copyright@y.st>
 * 
 * This program is free software: you can redistribute it and/or modify
 * it under the terms of the GNU General Public License as published by
 * the Free Software Foundation, either version 3 of the License, or
 * (at your option) any later version.
 * 
 * This program is distributed in the hope that it will be useful,
 * but WITHOUT ANY WARRANTY; without even the implied warranty of
 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
 * GNU General Public License for more details.
 * 
 * You should have received a copy of the GNU General Public License
 * along with this program. If not, see <https://www.gnu.org./licenses/>.
**/

$xhtml = array(
	'<{title}>' => 'backtracking',
	'takedown' => '2017-11-01',
	'<{body}>' => <<<END
<img src="/img/CC_BY-SA_4.0/y.st./weblog/2019/07.jpg" alt="Purple tree flowers" class="framed-centred-image" width="800" height="480"/>
<section id="diet">
	<h2>Dietary intake</h2>
	<p>
		I was too busy and tired today to do much as far as meals.
		I had a peanut butter and jelly sandwich for dinner, but for the rest of the day, just had pretzels (306 grams), corn chips (109 grams), and salsa (347 grams).
	</p>
</section>
<section id="errands">
	<h2>Errands</h2>
	<p>
		Before heading out today, I looked into getting my mobile&apos;s applications backed up.
		It turns out the application I was looking for to back up other applications was <a href="https://f-droid.org/en/packages/dk.jens.backup/">oandbackup</a>.
		That was a surprise.
		That&apos;s the one I used to use to back up application data, but I&apos;d forgotten that it was also the one that backs up applications themselves.
		I also chanced across a forum post saying that <a href="https://redmine.replicant.us/boards/33/topics/15053">T-Mobile is working on dropping {$a['3G']} support</a>.
		That&apos;s not good for Replicant users.
		I&apos;d need to ask in-store later to see if support was being dropped in this city.
	</p>
	<p>
		I dropped by the copy shop to get that one form from the clinic copied.
	</p>
	<p>
		Next, I dropped by the bottle-deposit place.
		Apparently, the person there couldn&apos;t fix the missing credit themself.
		They worked on their computer a bit, then said that when the boss read what they&apos;d entered, the boss&apos;d fix the credit.
		I&apos;m guessing it&apos;ll be fixed long before Sunday, which is when I&apos;ll try to use it again.
	</p>
	<p>
		When I stopped by the credit union to deposit my pay cheque, they asked me about a telephone number to put on the account again.
		Never going to happen, dude.
		It turns out they have a note on my account saying that I have no telephone service, but the teller thought the note seemed a bit ambiguous, like I might not have telephone service for the time being, but will get it soon.
		I disagreed, given the wording they told me the note had, but they added that I didn&apos;t have it by choice, thinking maybe that&apos;d get tellers to stop asking about it.
		Their idea, not mine.
		My idea is to just tell them I don&apos;t have telephone service every time they ask.
		They keep asking every once in a while, but I&apos;m still able to access my account.
	</p>
	<p>
		The person at the T-Mobile shop claims that there&apos;s still very good {$a['3G']} coverage in this city and will be for the foreseeable future.
		Setting up my tablet line when the battery arrives should be fine.
	</p>
	<p>
		I hit up the discount store for soy milk, which wasn&apos;t even worth mentioning, if not for a couple things that happened.
		First, I forgot to check the drawing number at the other store first.
		The Tuesday drawing is the whole reason I postpone my errands in this part of town until Tuesday!
		I can&apos;t go into the one store with a full load of soy milk from the other.
		I&apos;d have to make a second trip later in the day.
		As I got closer to home though, I realised I&apos;d left the paperwork I&apos;d copied at the discount store though!
		I&apos;d have to head back right away after dropping off my load at home.
		What a pain.
		When I got back though, the paperwork was luckily still there.
	</p>
</section>
<section id="drudgery">
	<h2>Drudgery</h2>
	<p>
		My discussion posts for the day:
	</p>
	<blockquote>
		<p>
			The paper I read was <a href="http://docs.media.bitpipe.com/io_10x/io_100229/item_410520/IBM_sSecurity_SO%23034252_E-Guide_051811.pdf">Database audit trail and compliance, database audit tools: auditing methods, configurations and filtering options</a>, linked to in my references section.
			Or were there other issues you were asking about where they were brought up?
		</p>
	</blockquote>
	<blockquote>
		<p>
			Yeah, I feel you there.
			I have my firewall set to block everything except for stuff that goes through my proxy.
			It prevents all data leaks without fail.
			But pretty much any tome I instruct someone to do something important, they get some part of it wrong.
			Computers are better at doing what they&apos;re told than people are.
		</p>
	</blockquote>
	<blockquote>
		<p>
			There&apos;s a lot that can be solved by not giving users excessive permissions.
			That applied to mire than just databases.
			For example, one of the major reasons Linux isn&apos;t very susceptible to viruses is that viruses have to run under some user&apos;s account, typically the account of the person that accidentally installed them, and Linux doesn&apos;t grant even the main user many permissions by default.
			They have to use the <code>root</code> account to actually administrate the computer.
			That means that when a virus runs on Linux, it can do damage to a user&apos;s personal files, but can&apos;t usually harm the system in any meaningful way.
			Occasionally, an exploit will be found to grant extra permissions so the virus can do more, but exploits are quickly patched in Linux.
			On Windows, on the other hand, the main user has way too many permissions, so on a single-user computer, viruses can really wreck havoc.
			(And that doesn&apos;t even mention the fact that Windows is more-easily exploitable and gets patches much slower.)
		</p>
		<p>
			I agree about the strong passwords, too.
			Personally, I recommend an encrypted password database that can generate passwords that are long, random strings.
			Personally, I use <a href="https://www.keepassx.org/">KeePassX</a> for that.
			It&apos;s available for Linux, OS X, and Windows.
			You make an interesting point about default account names.
			I wouldn&apos;t have thought anything of those, but it seems they&apos;re a target for brute force password attacks like you said.
		</p>
	</blockquote>
</section>
<section id="mouse">
	<h2>Broken mouse button</h2>
	<p>
		I was trying to clean junk out of the crack around my mouse buttons, and managed to rip the rubber under the left one.
		Now the left mouse button doesn&apos;t work very well.
		As it&apos;s built into my laptop, it&apos;s not as simple as swapping mice out.
		I&apos;m not sure what to do about it, but I guess it&apos;ll have to wait for the time being.
	</p>
</section>
END
);
